Quality of service management for interworking between different communication architectures

ABSTRACT

Procedures, systems, and devices for addressing quality of service (QoS) during an intersystem change of a wireless transmit/receive unit (WTRU) are discussed herein. A WTRU may send a protocol data unit (PDU) modification request to a network node, such as a session management function (SMF) device, indicating support for reflective quality of services (RQoS). In response to the modification request, the WTRU may then receive an acknowledgement, after which the WTRU may then be able to send data for a PDU of a specific RQoS. The RQoS may be specific to a single PDU or a plurality of PDUs. The modification request may include Session Management (SM) and/or Mobility Management (MM) information. The modification request may be included in an attach procedure or a tracking area update (TAU).

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application62/575,978 filed Oct. 23, 2017, U.S. Provisional Application 62/572,160filed Oct. 13, 2017, and U.S. Provisional Application 62/444,124 filedJan. 9, 2017, the contents of which are hereby incorporated by referenceherein.

BACKGROUND

In wireless communication system architecture, an evolved packet core(EPC) network is a framework for providing converged voice and data on aLTE network. As wireless standards evolve, the EPC may be used incombination with other types of core networks to facilitate a wirelesstransmit/receive unit (WTRU) to operate universally. In 5G networks, aNextGen core (NGC) network may operate, but how it will interwork withexisting networks needs to be addressed.

SUMMARY

Procedures, systems, and devices for addressing quality of service (QoS)during an inter-system change of a wireless transmit/receive unit (WTRU)are discussed herein. A WTRU may send a packet data unit (PDU)modification request to a network node, such as a session managementfunction (SMF) device, indicating support for reflective quality ofservice (RQoS). In response to the modification request, the WTRU maythen receive an acknowledgement, after which the WTRU may then be ableto send data for a PDU of a specific RQoS. The RQoS may be specific to asingle PDU or a plurality of PDUs. The modification request may includeSession Management (SM) and/or Mobility Management (MM) information. Themodification request may be included in an attach procedure or atracking area update (TAU).

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with the accompanying drawings,wherein like reference numerals in the figures indicate like elements,and wherein:

FIG. 1A is a system diagram illustrating an example communicationssystem in which one or more disclosed embodiments may be implemented;

FIG. 1B is a system diagram illustrating an example wirelesstransmit/receive unit (WTRU) that may be used within the communicationssystem illustrated in FIG. 1A according to an embodiment;

FIG. 1C is a system diagram illustrating an example radio access network(RAN) and an example core network (CN) that may be used within thecommunications system illustrated in FIG. 1A according to an embodiment;

FIG. 1D is a system diagram illustrating a further example RAN and afurther example CN that may be used within the communications systemillustrated in FIG. 1A according to an embodiment;

FIG. 2 is an example architecture of interworking between an EPC and aNextGen system according to one or more embodiments;

FIG. 3 is an example architecture of interworking between an EPC and aNextGen system according to one or more embodiments;

FIG. 4 is an example diagram of bearer based QoS model in EPC accordingto one or more embodiments;

FIG. 5 an example diagram of QoS model in NextGen according to one ormore embodiments;

FIG. 6 is an example procedure where a WTRU transfers from one system toanother according to one or more embodiment;

FIG. 7 is an example procedure for QoS rule generation for non-IP datathat use well known data protocols according to one or more embodiments;

FIG. 8 is an example procedure for QoS rule generation for non-IP datathat use proprietary data protocol according to one or more embodiments;and

FIG. 9 is an example procedure for addressing RQoS for one or morePDU(s) during an inter-system change.

DETAILED DESCRIPTION

FIG. 1A is a diagram illustrating an example communications system 100in which one or more disclosed embodiments may be implemented. Thecommunications system 100 may be a multiple access system that providescontent, such as voice, data, video, messaging, broadcast, etc., tomultiple wireless users. The communications system 100 may enablemultiple wireless users to access such content through the sharing ofsystem resources, including wireless bandwidth. For example, thecommunications systems 100 may employ one or more channel accessmethods, such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tailunique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM(UW-OFDM), resource block-filtered OFDM, filter bank multicarrier(FBMC), and the like.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a RAN104/113, a Core Network (CN) 106/115, a public switched telephonenetwork (PSTN) 108, the Internet 110, and other networks 112, though itwill be appreciated that the disclosed embodiments contemplate anynumber of WTRUs, base stations, networks, and/or network elements. TheCN may be representative of a NextGen Core (NGC) network, such as a 5Gsystem using New Radio (NR). Each of the WTRUs 102 a, 102 b, 102 c, 102d may be any type of device configured to operate and/or communicate ina wireless environment. By way of example, the WTRUs 102 a, 102 b, 102c, 102 d, any of which may be referred to as a “station” and/or a “STA”,may be configured to transmit and/or receive wireless signals and mayinclude a user equipment (UE), a mobile station, a fixed or mobilesubscriber unit, a subscription-based unit, a pager, a cellulartelephone, a personal digital assistant (PDA), a smartphone, a laptop, anetbook, a personal computer, a wireless sensor, a hotspot or Mi-Fidevice, an Internet of Things (IoT) device, a watch or other wearable, ahead-mounted display (HMD), a vehicle, a drone, a medical device andapplications (e.g., remote surgery), an industrial device andapplications (e.g., a robot and/or other wireless devices operating inan industrial and/or an automated processing chain contexts), a consumerelectronics device, a device operating on commercial and/or industrialwireless networks, and the like. Any of the WTRUs 102 a, 102 b, 102 cand 102 d may be interchangeably referred to as a UE.

The communications systems 100 may also include a base station 114 aand/or a base station 114 b. Each of the base stations 114 a, 114 b maybe any type of device configured to wirelessly interface with at leastone of the WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to oneor more communication networks, such as the CN 106/115, the Internet110, and/or the other networks 112. By way of example, the base stations114 a, 114 b may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller,an access point (AP), a wireless router, and the like. While the basestations 114 a, 114 b are each depicted as a single element, it will beappreciated that the base stations 114 a, 114 b may include any numberof interconnected base stations and/or network elements.

The base station 114 a may be part of the RAN 104/113, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals on one or morecarrier frequencies, which may be referred to as a cell (not shown).These frequencies may be in licensed spectrum, unlicensed spectrum, or acombination of licensed and unlicensed spectrum. A cell may providecoverage for a wireless service to a specific geographical area that maybe relatively fixed or that may change over time. The cell may furtherbe divided into cell sectors. For example, the cell associated with thebase station 114 a may be divided into three sectors. Thus, in oneembodiment, the base station 114 a may include three transceivers, i.e.,one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and mayutilize multiple transceivers for each sector of the cell. For example,beamforming may be used to transmit and/or receive signals in desiredspatial directions.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet(UV), visible light, etc.). The air interface 116 may be establishedusing any suitable radio access technology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104/113 and the WTRUs 102 a,102 b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA), whichmay establish the air interface 115/116/117 using wideband CDMA (WCDMA).WCDMA may include communication protocols such as High-Speed PacketAccess (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-SpeedDownlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access(HSUPA).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as Evolved UMTS TerrestrialRadio Access (E-UTRA), which may establish the air interface 116 usingLong Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/orLTE-Advanced Pro (LTE-A Pro).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as New Radio (NR) Radio Access,which may establish the air interface 116 using (NR).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement multiple radio access technologies. For example, thebase station 114 a and the WTRUs 102 a, 102 b, 102 c may implement LTEradio access and NR radio access together, for instance using dualconnectivity (DC) principles. Thus, the air interface utilized by WTRUs102 a, 102 b, 102 c may be characterized by multiple types of radioaccess technologies and/or transmissions sent to/from multiple types ofbase stations (e.g., a eNB and a gNB).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.11 (i.e.,Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperabilityfor Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×, CDMA2000 EV-DO,Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), InterimStandard 856 (IS-856), Global System for Mobile communications (GSM),Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and thelike.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, an industrialfacility, an air corridor (e.g., for use by drones), a roadway, and thelike. In one embodiment, the base station 114 b and the WTRUs 102 c, 102d may implement a radio technology such as IEEE 802.11 to establish awireless local area network (WLAN). In an embodiment, the base station114 b and the WTRUs 102 c, 102 d may implement a radio technology suchas IEEE 802.15 to establish a wireless personal area network (WPAN). Inyet another embodiment, the base station 114 b and the WTRUs 102 c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. Asshown in FIG. 1A, the base station 114 b may have a direct connection tothe Internet 110. Thus, the base station 114 b may not be required toaccess the Internet 110 via the CN 106/115.

The RAN 104/113 may be in communication with the CN 106/115, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. The data may have varying qualityof service (QoS) requirements, such as differing throughputrequirements, latency requirements, error tolerance requirements,reliability requirements, data throughput requirements, mobilityrequirements, and the like. The CN 106/115 may provide call control,billing services, mobile location-based services, pre-paid calling,Internet connectivity, video distribution, etc., and/or performhigh-level security functions, such as user authentication. Although notshown in FIG. 1A, it will be appreciated that the RAN 104/113 and/or theCN 106/115 may be in direct or indirect communication with other RANsthat employ the same RAT as the RAN 104/113 or a different RAT. Forexample, in addition to being connected to the RAN 104/113, which may beutilizing a NR radio technology, the CN 106/115 may also be incommunication with another RAN (not shown) employing a GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN 106/115 may also serve as a gateway for the WTRUs 102 a, 102 b,102 c, 102 d to access the PSTN 108, the Internet 110, and/or the othernetworks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) and/orthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired and/or wireless communications networksowned and/or operated by other service providers. For example, thenetworks 112 may include another CN connected to one or more RANs, whichmay employ the same RAT as the RAN 104/113 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities (e.g., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks). For example, the WTRU 102 c shown in FIG. 1A may be configuredto communicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram illustrating an example WTRU 102. As shownin FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120,a transmit/receive element 122, a speaker/microphone 124, a keypad 126,a display/touchpad 128, non-removable memory 130, removable memory 132,a power source 134, a global positioning system (GPS) chipset 136,and/or other peripherals 138, among others. It will be appreciated thatthe WTRU 102 may include any sub-combination of the foregoing elementswhile remaining consistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In an embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and/or receive both RF and light signals. It will beappreciated that the transmit/receive element 122 may be configured totransmit and/or receive any combination of wireless signals.

Although the transmit/receive element 122 is depicted in FIG. 1B as asingle element, the WTRU 102 may include any number of transmit/receiveelements 122. More specifically, the WTRU 102 may employ MIMOtechnology. Thus, in one embodiment, the WTRU 102 may include two ormore transmit/receive elements 122 (e.g., multiple antennas) fortransmitting and receiving wireless signals over the air interface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as NR and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs and/or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, a Virtual Reality and/or Augmented Reality (VR/AR) device, anactivity tracker, and the like. The peripherals 138 may include one ormore sensors, the sensors may be one or more of a gyroscope, anaccelerometer, a hall effect sensor, a magnetometer, an orientationsensor, a proximity sensor, a temperature sensor, a time sensor; ageolocation sensor; an altimeter, a light sensor, a touch sensor, amagnetometer, a barometer, a gesture sensor, a biometric sensor, and/ora humidity sensor.

The WTRU 102 may include a full duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for both the UL (e.g., for transmission) anddownlink (e.g., for reception) may be concurrent and/or simultaneous.The full duplex radio may include an interference management unit 139 toreduce and or substantially eliminate self-interference via eitherhardware (e.g., a choke) or signal processing via a processor (e.g., aseparate processor (not shown) or via processor 118). In an embodiment,the WRTU 102 may include a half-duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for either the UL (e.g., for transmission) or thedownlink (e.g., for reception)).

FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106according to an embodiment. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102c over the air interface 116. The RAN 104 may also be in communicationwith the CN 106.

The RAN 104 may include eNode-Bs 160 a, 160 b, 160 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 160 a, 160 b, 160c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the eNode-Bs 160 a, 160 b, 160 c may implement MIMO technology. Thus,the eNode-B 160 a, for example, may use multiple antennas to transmitwireless signals to, and/or receive wireless signals from, the WTRU 102a.

Each of the eNode-Bs 160 a, 160 b, 160 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the UL and/or DL, and the like. As shown in FIG. 10, the eNode-Bs 160a, 160 b, 160 c may communicate with one another over an X2 interface.

The CN 106 shown in FIG. 10 may include a mobility management entity(MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN)gateway (or PGW) 166. While each of the foregoing elements are depictedas part of the CN 106, it will be appreciated that any of these elementsmay be owned and/or operated by an entity other than the CN operator.

The MME 162 may be connected to each of the eNode-Bs 162 a, 162 b, 162 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 162 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aparticular serving gateway during an initial attach of the WTRUs 102 a,102 b, 102 c, and the like. The MME 162 may provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as GSM and/or WCDMA.

The SGW 164 may be connected to each of the eNode Bs 160 a, 160 b, 160 cin the RAN 104 via the S1 interface. The SGW 164 may generally route andforward user data packets to/from the WTRUs 102 a, 102 b, 102 c. The SGW164 may perform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when DL data is available forthe WTRUs 102 a, 102 b, 102 c, managing and storing contexts of theWTRUs 102 a, 102 b, 102 c, and the like.

The SGW 164 may be connected to the PGW 166, which may provide the WTRUs102 a, 102 b, 102 c with access to packet-switched networks, such as theInternet 110, to facilitate communications between the WTRUs 102 a, 102b, 102 c and IP-enabled devices.

The CN 106 may facilitate communications with other networks. Forexample, the CN 106 may provide the WTRUs 102 a, 102 b, 102 c withaccess to circuit-switched networks, such as the PSTN 108, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and traditionalland-line communications devices. For example, the CN 106 may include,or may communicate with, an IP gateway (e.g., an IP multimedia subsystem(IMS) server) that serves as an interface between the CN 106 and thePSTN 108. In addition, the CN 106 may provide the WTRUs 102 a, 102 b,102 c with access to the other networks 112, which may include otherwired and/or wireless networks that are owned and/or operated by otherservice providers.

Although the WTRU is described in FIGS. 1A-1D as a wireless terminal, itis contemplated that in certain representative embodiments that such aterminal may use (e.g., temporarily or permanently) wired communicationinterfaces with the communication network.

In representative embodiments, the other network 112 may be a WLAN.

A WLAN in Infrastructure Basic Service Set (BSS) mode may have an AccessPoint (AP) for the BSS and one or more stations (STAs) associated withthe AP. The AP may have an access or an interface to a DistributionSystem (DS) or another type of wired/wireless network that carriestraffic in to and/or out of the BSS. Traffic to STAs that originatesfrom outside the BSS may arrive through the AP and may be delivered tothe STAs. Traffic originating from STAs to destinations outside the BSSmay be sent to the AP to be delivered to respective destinations.Traffic between STAs within the BSS may be sent through the AP, forexample, where the source STA may send traffic to the AP and the AP maydeliver the traffic to the destination STA. The traffic between STAswithin a BSS may be considered and/or referred to as peer-to-peertraffic. The peer-to-peer traffic may be sent between (e.g., directlybetween) the source and destination STAs with a direct link setup (DLS).In certain representative embodiments, the DLS may use an 802.11e DLS oran 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS)mode may not have an AP, and the STAs (e.g., all of the STAs) within orusing the IBSS may communicate directly with each other. The IBSS modeof communication may sometimes be referred to herein as an “ad-hoc” modeof communication.

When using the 802.11ac infrastructure mode of operation or a similarmode of operations, the AP may transmit a beacon on a fixed channel,such as a primary channel. The primary channel may be a fixed width(e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.The primary channel may be the operating channel of the BSS and may beused by the STAs to establish a connection with the AP. In certainrepresentative embodiments, Carrier Sense Multiple Access with CollisionAvoidance (CSMA/CA) may be implemented, for example in in 802.11systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, maysense the primary channel. If the primary channel is sensed/detectedand/or determined to be busy by a particular STA, the particular STA mayback off. One STA (e.g., only one station) may transmit at any giventime in a given BSS.

High Throughput (HT) STAs may use a 40 MHz wide channel forcommunication, for example, via a combination of the primary 20 MHzchannel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHzwide channel.

Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz,and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may beformed by combining contiguous 20 MHz channels. A 160 MHz channel may beformed by combining 8 contiguous 20 MHz channels, or by combining twonon-contiguous 80 MHz channels, which may be referred to as an 80+80configuration. For the 80+80 configuration, the data, after channelencoding, may be passed through a segment parser that may divide thedata into two streams. Inverse Fast Fourier Transform (IFFT) processing,and time domain processing, may be done on each stream separately. Thestreams may be mapped on to the two 80 MHz channels, and the data may betransmitted by a transmitting STA. At the receiver of the receiving STA,the above described operation for the 80+80 configuration may bereversed, and the combined data may be sent to the Medium Access Control(MAC).

Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. Thechannel operating bandwidths, and carriers, are reduced in 802.11af and802.11ah relative to those used in 802.11n, and 802.11ac. 802.11afsupports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space(TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and16 MHz bandwidths using non-TVWS spectrum. According to a representativeembodiment, 802.11ah may support Meter Type Control/Machine-TypeCommunications, such as MTC devices in a macro coverage area. MTCdevices may have certain capabilities, for example, limited capabilitiesincluding support for (e.g., only support for) certain and/or limitedbandwidths. The MTC devices may include a battery with a battery lifeabove a threshold (e.g., to maintain a very long battery life).

WLAN systems, which may support multiple channels, and channelbandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include achannel which may be designated as the primary channel. The primarychannel may have a bandwidth equal to the largest common operatingbandwidth supported by all STAs in the BSS. The bandwidth of the primarychannel may be set and/or limited by a STA, from among all STAs inoperating in a BSS, which supports the smallest bandwidth operatingmode. In the example of 802.11ah, the primary channel may be 1 MHz widefor STAs (e.g., MTC type devices) that support (e.g., only support) a 1MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.Carrier sensing and/or Network Allocation Vector (NAV) settings maydepend on the status of the primary channel. If the primary channel isbusy, for example, due to a STA (which supports only a 1 MHz operatingmode), transmitting to the AP, the entire available frequency bands maybe considered busy even though a majority of the frequency bands remainsidle and may be available.

In the United States, the available frequency bands, which may be usedby 802.11ah, are from 902 MHz to 928 MHz. In Korea, the availablefrequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the availablefrequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidthavailable for 802.11ah is 6 MHz to 26 MHz depending on the country code.

FIG. 1D is a system diagram illustrating the RAN 113 and the CN 115according to an embodiment. As noted above, the RAN 113 may employ an NRradio technology to communicate with the WTRUs 102 a, 102 b, 102 c overthe air interface 116. The RAN 113 may also be in communication with theCN 115.

The RAN 113 may include gNBs 180 a, 180 b, 180 c, though it will beappreciated that the RAN 113 may include any number of gNBs whileremaining consistent with an embodiment. The gNBs 180 a, 180 b, 180 cmay each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the gNBs 180 a, 180 b, 180 c may implement MIMO technology. For example,gNBs 180 a, 108 b may utilize beamforming to transmit signals to and/orreceive signals from the gNBs 180 a, 180 b, 180 c. Thus, the gNB 180 a,for example, may use multiple antennas to transmit wireless signals to,and/or receive wireless signals from, the WTRU 102 a. In an embodiment,the gNBs 180 a, 180 b, 180 c may implement carrier aggregationtechnology. For example, the gNB 180 a may transmit multiple componentcarriers to the WTRU 102 a (not shown). A subset of these componentcarriers may be on unlicensed spectrum while the remaining componentcarriers may be on licensed spectrum. In an embodiment, the gNBs 180 a,180 b, 180 c may implement Coordinated Multi-Point (CoMP) technology.For example, WTRU 102 a may receive coordinated transmissions from gNB180 a and gNB 180 b (and/or gNB 180 c).

The WTRUs 102 a, 102 b, 102 c may communicate with gNBs 180 a, 180 b,180 c using transmissions associated with a scalable numerology. Forexample, the OFDM symbol spacing and/or OFDM subcarrier spacing may varyfor different transmissions, different cells, and/or different portionsof the wireless transmission spectrum. The WTRUs 102 a, 102 b, 102 c maycommunicate with gNBs 180 a, 180 b, 180 c using subframe or transmissiontime intervals (TTIs) of various or scalable lengths (e.g., containingvarying number of OFDM symbols and/or lasting varying lengths ofabsolute time).

The gNBs 180 a, 180 b, 180 c may be configured to communicate with theWTRUs 102 a, 102 b, 102 c in a standalone configuration and/or anon-standalone configuration. In the standalone configuration, WTRUs 102a, 102 b, 102 c may communicate with gNBs 180 a, 180 b, 180 c withoutalso accessing other RANs (e.g., such as eNode-Bs 160 a, 160 b, 160 c).In the standalone configuration, WTRUs 102 a, 102 b, 102 c may utilizeone or more of gNBs 180 a, 180 b, 180 c as a mobility anchor point. Inthe standalone configuration, WTRUs 102 a, 102 b, 102 c may communicatewith gNBs 180 a, 180 b, 180 c using signals in an unlicensed band. In anon-standalone configuration WTRUs 102 a, 102 b, 102 c may communicatewith/connect to gNBs 180 a, 180 b, 180 c while also communicatingwith/connecting to another RAN such as eNode-Bs 160 a, 160 b, 160 c. Forexample, WTRUs 102 a, 102 b, 102 c may implement DC principles tocommunicate with one or more gNBs 180 a, 180 b, 180 c and one or moreeNode-Bs 160 a, 160 b, 160 c substantially simultaneously. In thenon-standalone configuration, eNode-Bs 160 a, 160 b, 160 c may serve asa mobility anchor for WTRUs 102 a, 102 b, 102 c and gNBs 180 a, 180 b,180 c may provide additional coverage and/or throughput for servicingWTRUs 102 a, 102 b, 102 c.

Each of the gNBs 180 a, 180 b, 180 c may be associated with a particularcell (not shown) and may be configured to handle radio resourcemanagement decisions, handover decisions, scheduling of users in the ULand/or DL, support of network slicing, dual connectivity, interworkingbetween NR and E-UTRA, routing of user plane data towards User PlaneFunction (UPF) 184 a, 184 b, routing of control plane informationtowards Access and Mobility Management Function (AMF) 182 a, 182 b andthe like. As shown in FIG. 1D, the gNBs 180 a, 180 b, 180 c maycommunicate with one another over an Xn interface.

The CN 115 shown in FIG. 1D may include at least one AMF 182 a, 182 b,at least one UPF 184 a,184 b, at least one Session Management Function(SMF) 183 a, 183 b, and possibly a Data Network (DN) 185 a, 185 b. TheAMF 182 a, 182 b, UPF 184 a,184 b, and SMF 183 a, 183 b may be the sameor different types of devices, the hardware of those devices maycomprise of a processor, memory, transceiver, and other data interfacesas necessary. In one example, the AMF 182 a, 182 b, UPF 184 a,184 b, andSMF 183 a, 183 b hardware may be similar to the hardware of a WTRU asdescribed herein. In another example, each of the AMF 182 a, 182 b, UPF184 a,184 b, and SMF 183 a, 183 b may comprise of more than one device.While each of the foregoing elements are depicted as part of the CN 115,it will be appreciated that any of these elements may be owned and/oroperated by an entity other than the CN operator.

The AMF 182 a, 182 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N2 interface and may serve as acontrol node. For example, the AMF 182 a, 182 b may be responsible forauthenticating users of the WTRUs 102 a, 102 b, 102 c, support fornetwork slicing (e.g., handling of different PDU sessions with differentrequirements), selecting a particular SMF 183 a, 183 b, management ofthe registration area, termination of NAS signaling, mobilitymanagement, and the like. Network slicing may be used by the AMF 182 a,182 b in order to customize CN support for WTRUs 102 a, 102 b, 102 cbased on the types of services being utilized WTRUs 102 a, 102 b, 102 c.For example, different network slices may be established for differentuse cases such as services relying on ultra-reliable low latency (URLLC)access, services relying on enhanced massive mobile broadband (eMBB)access, services for machine type communication (MTC) access, and/or thelike. The AMF 162 may provide a control plane function for switchingbetween the RAN 113 and other RANs (not shown) that employ other radiotechnologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP accesstechnologies such as WiFi.

The SMF 183 a, 183 b may be connected to an AMF 182 a, 182 b in the CN115 via an N11 interface. The SMF 183 a, 183 b may also be connected toa UPF 184 a, 184 b in the CN 115 via an N4 interface. The SMF 183 a, 183b may select and control the UPF 184 a, 184 b and configure the routingof traffic through the UPF 184 a, 184 b. The SMF 183 a, 183 b mayperform other functions, such as managing and allocating UE IP address,managing PDU sessions, controlling policy enforcement and QoS, providingdownlink data notifications, and the like. A PDU session type may beIP-based, non-IP based, Ethernet-based, and the like.

The UPF 184 a, 184 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N3 interface, which may provide theWTRUs 102 a, 102 b, 102 c with access to packet-switched networks, suchas the Internet 110, to facilitate communications between the WTRUs 102a, 102 b, 102 c and IP-enabled devices. The UPF 184, 184 b may performother functions, such as routing and forwarding packets, enforcing userplane policies, supporting multi-homed PDU sessions, handling user planeQoS, buffering downlink packets, providing mobility anchoring, and thelike.

The CN 115 may facilitate communications with other networks. Forexample, the CN 115 may include, or may communicate with, an IP gateway(e.g., an IP multimedia subsystem (IMS) server) that serves as aninterface between the CN 115 and the PSTN 108. In addition, the CN 115may provide the WTRUs 102 a, 102 b, 102 c with access to the othernetworks 112, which may include other wired and/or wireless networksthat are owned and/or operated by other service providers. In oneembodiment, the WTRUs 102 a, 102 b, 102 c may be connected to a localData Network (DN) 185 a, 185 b through the UPF 184 a, 184 b via the N3interface to the UPF 184 a, 184 b and an N6 interface between the UPF184 a, 184 b and the DN 185 a, 185 b.

In view of FIGS. 1A-1D, and the corresponding description of FIGS.1A-1D, one or more, or all, of the functions described herein withregard to one or more of: WTRU 102 a-d, Base Station 114 a-b, eNode-B160 a-c, MME 162, SGW 164, PGW 166, gNB 180 a-c, AMF 182 a-ab, UPF 184a-b, SMF 183 a-b, DN 185 a-b, and/or any other device(s) describedherein, may be performed by one or more emulation devices (not shown).The emulation devices may be one or more devices configured to emulateone or more, or all, of the functions described herein. For example, theemulation devices may be used to test other devices and/or to simulatenetwork and/or WTRU functions.

The emulation devices may be designed to implement one or more tests ofother devices in a lab environment and/or in an operator networkenvironment. For example, the one or more emulation devices may performthe one or more, or all, functions while being fully or partiallyimplemented and/or deployed as part of a wired and/or wirelesscommunication network in order to test other devices within thecommunication network. The one or more emulation devices may perform theone or more, or all, functions while being temporarilyimplemented/deployed as part of a wired and/or wireless communicationnetwork. The emulation device may be directly coupled to another devicefor purposes of testing and/or may performing testing using over-the-airwireless communications.

The one or more emulation devices may perform the one or more, includingall, functions while not being implemented/deployed as part of a wiredand/or wireless communication network. For example, the emulationdevices may be utilized in a testing scenario in a testing laboratoryand/or a non-deployed (e.g., testing) wired and/or wirelesscommunication network in order to implement testing of one or morecomponents. The one or more emulation devices may be test equipment.Direct RF coupling and/or wireless communications via RF circuitry(e.g., which may include one or more antennas) may be used by theemulation devices to transmit and/or receive data.

FIG. 2 shows an example of an architecture for tight interworking of anevolved packet core (EPC) network and a NextGen (NG) core (NGC) network.According to the example of FIG. 2, a Home Subscriber Server (HSS) 202may communicate with an NGC 204. An operator may deploy an NG RAN 208,such as for 5G new radio (NR), in conjunction with an EPC and upgrade,or “evolve”, all the installed E-UTRAN nodes 206 to support the new NGC204. The NGC 204 may communicate with the “Evolved” E-UTRAN 206 and theNG RAN 208 over an N2/N3 interface, 222 a and 222 b respectively. TheNGC 204 may communicate with an NGC WTRU 205 a and 205 b over an N1connection, 220 a and 220 b, respectively. In this example, servicecontinuity to a NGC WTRU, such as 205 a or 205 b, is only providedbetween the “Evolved” E-UTRAN 206 and the NG RAN 208 connected to theNGC 204. Further, when an E-UTRAN is “Evolved” by supporting access tothe NGC 20, then interworking, such as idle and connected mode mobility,may be performed using NGC procedures.

FIG. 3 shows an example of an architecture for the interworking of anEPC and an NG CN where there is non-roaming and roaming with localbreakout possibilities. In the example of FIG. 3, an operator of an EPC310 has not upgraded installed E-UTRAN node(s) 307, has upgraded or“Evolved” some installed E-UTRAN node(s) 306 to support the new NGC 304over N2/N3 321 a, or has deployed an E-UTRAN/NR 309 scenario, also knownas an “Option 3”, for macro coverage with a stand-alone NR componentconnected to the NGC (e.g., for small cells). Option 3 309 may providefor dual connectivity deployments where E-UTRA may be the anchor radioaccess technology (RAT) and NR may be the secondary RAT connected to EPCvia an eNB. Further, core network interworking between EPC 310 and NGC304 may be provided for full service continuity. Interfaces Nx 324 andNy 325 may be introduced between the MME 313 and SGW 315 respectivelyand the Nz 326 interface may be defined between the SGW 315 and the CPfunction 318 in order to enable interworking between the EPC 310 and theNGC 304. Nx 324 and Ny 325 may be inter-core network interfaces for thec-plane and u-plane respectively and may correspond to inter-NGCinterfaces. Additionally, N4 323 interfaces may be introduced betweenthe CP functions 318 and UP functions 316. The NG point coordinationfunction (PCF) 314 may be involved if policy and charging is controlledin a dynamic manner. The NG PCF 314 may be capable of supportingfunctionalities of Evolved Packet System (EPS) policy and changing rulesfunction (PCRF).

In the example of FIG. 3, in one scenario when connecting to a E-UTRAN,such as 307 and/or 309, a WTRU, such as the NGC WTRU 305 c, may use EPCNAS 330 a and 330 b. In such a scenario, when connected to a non-evolvedE-UTRAN 307 and 309, the WTRU authentication, mobility management, andsession management may be performed by the MME 312 towards the NGC WTRU305 c.

Further in FIG. 3, in order to support idle or connected mode mobilitybetween the EPC 310 and the NGC 304, the WTRU's serving MME 313 mayconnect via a control plane Nx 324 interface to CP functions 318 in theNGC 304, and the WTRU's serving SGW 314 may connect via a user plane Ny325 interface to UP functions 316 and via a control plane Nz 326interface to CP functions 318. The user plane may always be anchored inNGC 304 for NGC WTRU 305 c with an associated subscription. The GWselection may be done by the MME 313, and based on a WTRU subscriptionthat enables 5G, the GW selection may result in a selection of a GW inthe NGC 304.

As discussed herein, for interworking with NGC 304 an NGC WTRU 305 c mayperform an initial attach over E-UTRAN 307 or 309 using EPC NAS 330 a or330 b respectively and later move to an Evolved E-UTRAN 306 or NG RAN308 connected with N1 320 a and 320 b (i.e., NG NAS) by interworkingwith the NGC 304 (e.g., moving a WTRU context from the EPC 310 to theNGC 304). During an initial attach a WTRU user plane may be anchored inthe UP function 318 provided by the NGC 304 to support mobility.Interworking with a NGC 304 may also be performed by enabling an NGCWTRU 305 a and/or 305 b to perform an initial attach and sessionmanagement over “Evolved” E-UTRAN 306 using N1 320 a or NG RAN 308 usingN1 320 b, respectively; the NGC WTRUs 305 a and/or 305 b may then latermove to E-UTRAN 307 using EPC NAS 330 a and/or E-UTRAN Option 3 309using EPC NAS 330 b, respectively, by interworking with the NGC 304(e.g., moving the WTRU 305 a and/or 305 b context from the NGC 304).

Service continuity may be provided between the E-UTRAN and the NG RANoptions deployed by the operator via the Interworking Function and thecommon anchoring of the user plane.

FIG. 4 is an example of a bearer based on a QoS model in an EPC. A WTRU402 may be connected over a Uu 420 to an eNB 404. The eNB 404 may beconnected to an S-GW 406 via an S1-U connection 422. The S-GW 406 may beconnected over an S5 connection 424 to a PGW 408. The PGW 408 may beconnected to a Packet Data Network (PDN) 410 over an SGi 426 connection.The WTRU 402 may have a PDN connection 421 through the EPC to the PDN410.

In this example, packets with different QoS characteristics, such as QoSClass Identifier (QCI) values in the EPC, are filtered into differentend to end bearers between the WTRU 402 and the core network (e.g., PGW408). There may be different flows such as IP flows 410, 412, 414, 416,and 418. In the example of FIG. 4, IP flows may require similar QoStreatment and may be grouped together, such as QoS x 413 which groups IPflows 412 and 414 or QoS y 417 which groups IP flows 416 and 418. The IPflows requiring similar QoS in the downlink are placed in the dedicatedbearers (DBs) that can meet the QoS requirements of that IP flow, suchas where DB 432 may be associated with a QCI of QoS x 413 and DB 434 maybe associated with a QCI of a QoS y 417. In the example of FIG. 4, adefault bearer 430 may be the first EPS bearer that is establishedsimultaneously with the PDN connection; also, it may be associated withsome default QoS treatments. IP flows that do not require specific QoStreatment and can be satisfied with default QoS treatment may go to thedefault bearer 430. A similar procedure (not shown) may happen at theWTRU in the uplink direction. The end to end QoS tunnel in EPC mayconsist of an S5 424 tunnel between PGW 406 & SGW 408, and/or an S1-Utunnel 422 between the SGW 408 & eNB 404. Further in FIG. 4, the packetflowing through a particular bearer or tunnel meets the same QoStreatment as it flows through these three tunnels (i.e., S5, S1-U andUu) between the different nodes both in the uplink and downlinkdirection.

FIG. 5 is an example of a user plane architecture for QoS management inan NG system. The architecture may comprise a WTRU 502 connected over NGradio 520 to a NextGen RAN (NG RAN) 504. The NG RAN 504 may be connectedover an N3 interface 522 to an UP-GW 506. The UP-GW 506 may be connectedto a Data Network (DN) 508 over a N6 interface 524. The DN 508 may havea PDU connection 521 to the WTRU 502 through this NGC.

In FIG. 5, unlike FIG. 4, dedicated bearers may not be implemented inthe NGC and instead there may be a single tunnel (N3 interface) betweenthe NG RAN 504 and User Plane Gateway (UP-GW) 506 through which allpackets flow. Packet marking as part of the packet header may be used toidentify IP packets from a data network (DN) 508 that require differentQoS treatments, such as flow 1, 2, and 4 with QoS x 410, QoS y 412, andQoS z 414 respectively; in this example QoS x 410, QoS y 412, and QoS z414 may be varying levels/degrees of QoS requirements for data containedin the IP packets of each flow. The marking is performed by the UP-GW506 in the downlink direction and by the NG RAN 504 in the uplinkdirection. Based on the packet marking the NG RAN 504 may decide toplace the packets in different dedicated radio bearers (DRBs) onceoutside the NGC, such as DRB 530, 531, and 533. The data with QoS x 410,QoS y 412, and QoS z 414 may be placed in DRB 530, 531, and 533respectively, with each DRB being assigned one IP flow of dataassociated with one QoS. Each DRB may be created to meet the QoSrequirement such as packet delay budget and/or packet error rate, etc.,for different IP flows.

In one embodiment, there may be procedures to ensure interworking of QoStreatment between EPC and NextGen systems is maintained. In one scenariowhere the WTRU moves between the EPC system and NextGen system thehandover may be seamless—service continuity is maintained—both in thedirection from EPC to NextGen system and from NextGen system to EPC. Ifthe handover is seamless, then from the perspective of applicationsrunning on a WTRU, the QoS treatment for a particular IP flow may be thesame. Procedures as discussed herein may ensure the seamless nature whenthe WTRU is moving between a NG and EPC system, or vice versa.

In one embodiment addressing QoS interworking between the NGC and EPC,the NG CP-Functions (Fxn), also referred to as an NG-CP, may perform anaction such as sending new uplink traffic flow templates (TFTs) and/orpacket filters to a WTRU. In an NG system, the packet filters may besent to the WTRU by the RAN node meaning there may be no packet filtersat the NAS level. Upon handing over to the E-UTRAN, the CP-Fxn may needto send the UL packet filters to the WTRU since the IP flows need to beseparated into various dedicated bearers above the packet dataconvergence protocol (PDCP) level in the WTRU. The CP-Fxn may imitate N1signaling between the WTRU by sending a modify bearer request message tothe WTRU. One or more pieces of information may be included in the TFTsor the message sent over N1 to the WTRU.

In some embodiments there may be a Reflective QoS (RQoS) where areceived stream/packet has a given QoS, and responding to thatstream/packet will entail using the same QoS or a QoS that is based onthe QoS of the received stream/packet, thereby being “reflective.” Inother words, a QoS may not be pre negotiated or pre setup with thenode/party that transmitted the stream/packet for situations where RQoSis used, and instead may be reflected based on the QoS of the receivedstream/packet. Information included in the TFTs or the message sent overN1 to the WTRU may be an indication that an RQoS indication (RQI) is notapplicable anymore. This indication may be part of explicit controlplane signaling or the network may not include the RQI in the user planepacket (or packet header) sent to the WTRU.

Information included in the TFTs or the message sent over N1 to the WTRUmay also be a mapping between QCI and flow based packet marking rules,such as a flow priority indicator (FPI), which may be sent to the WTRUby the CP-Fxn. This mapping may be a static mapping, such as where forevery QCI there would be a corresponding FPI value. Alternatively, thenetwork may send a dynamic mapping where for each service, an FPI ofthat service corresponds to an appropriate (different) or same QCIvalue. This concept may be applied to a case where the WTRU has multipleprotocol data unit (PDU) connections for different services. In such acase, the CP-Fxn may send a different QCI-FPI mapping for each PDUconnection. The CP-Fxn may make the mapping determination based on thePDU connection parameters (e.g., service type, slice type serving thePDU connection, WTRU capabilities, subscription information, and/orlocal policies).

Information included in the TFTs or the message sent over N1 to the WTRUmay also be a packet marking information, determined by the NG, based onthe intent level rules for a particular application possibly receivingsuch information from an application server. The intent level rules maynot be applicable to the EPC system because of the bearer based model,hence, if intent level rules apply to an IP flow, the CP-Fxn may takethe following actions: Inform the application server that the flow hasbeen moved to the EPC system; request the application server or thepolicy node to convert the intent level QoS rules to the best possibletransport level QoS rules; based on the actions described herein, theCP-Fxn may receive the transport level QoS rules, such as a particularFPI value, which may then be mapped to QCI by the CP-Fxn as previouslydescribed herein.

The NG CP-Fxns may also perform N2 signaling (between CP-Fxn and RAN) tothe network. The CP-Fxn may have or may derive QCI information based onQoS characteristics for a particular PDU connection. The CP-Fxn mayinteract with a policy node and/or user subscription database todetermine QCI values. Further, the CP-Fxn may send the mapping betweenthe QCI and FPI (user plane marking) to the evolved eNB. This action maybe required by the CP-Fxn since the user plane packets carried by the N3tunnel between the UP-GW and eNB in the downlink direction may stillhave the marking as part of the packet header. The eNB may need to haveinformation to convert the packet marking information to the QCI thatmay then be applied by the eNB to transmit the packet to the WTRU over aUu interface by means of one or more data radio bearers (DRBs).Moreover, this mapping information may be used by the eNB to mark thepackets received from the WTRU in the uplink direction before sendingthem to the UP-GW over the N3 tunnel.

Additionally, the NG CP-Fxns may perform an N3 interface update in asituation where there may be additional packet markings to specify theQCI value in the user plane packets, and therefore there may be norequirement to send the QCI to FPI mapping to the eNB as describedherein.

FIG. 6 shows a procedure that may be implemented utilizing theembodiments discussed herein concerning a network node in a 5G wirelesscommunications system where a WTRU 608 is handed over from a NG systemto an EPC system. An FPI to QCI mapping may be retrieved 603 from apolicy server/Fxn by an NG CP 602. The NG CP 602 may then generate ULTFTs to enable the WTRU 608 to separate the 5G data flows into aplurality of dedicated bearers. The generated UL TFTs may each includean indication that the RQI may not be applicable in the EPC system. TheNG CP 602 may send 605 the FPI to QCI mapping and EPS bearer identity toNG3 tunnel identity mapping to an eNB 606. The NG CP 602 may then send607 the generated UL TFTs and FPI to QCI mapping information to the WTRU608. The NG CP 602 may then send 609 a message that the 5G data flowshave been handed over to the EPC system to an application server/Fxn610.

In one embodiment addressing QoS interworking between the NG and EPC,the MME may perform actions upon handover to the EPC, such as triggernetwork initiated Modify Bearer Request (MBR) or Create Bearer Request(CBR) procedure to establish dedicated bearers for different FPI values.Alternatively or additionally, the MME may receive authorized FPI valuesfor PDU connections active at the WTRU, which means the MME may have toconvert the FPI values to QCI values. The MME may interact with the PCFand/or HSS to determine the conversion of FPI values to the QCI values.

In one embodiment addressing QoS interworking between the NG and EPC,the WTRU may perform a tracking area update (TAU) for idle mode mobilitycases. Alternatively, the WTRU may perform a registration update when itmoves from the NG system to the EPC system. In the event of eitheraction, the WTRU may include certain information in the TAU request orother NAS message to the MME, such as when the WTRU communicates withthe MME after moving to the EPC system, as is possible in the example ofFIG. 3. Such information may include one or more of the following:pre-authorized FPI (the FPI values that were authorized by the CP-Fxn atthe time of PDU session establishment); other FPI values, such as otherthan the pre-authorized values, used by the WTRU for a particular PDUconnection (e.g., the WTRU has requested additional QoS support for IPflows during an on-going PDU connection); and/or, an indication ofwhether RQoS applies correspondingly to the authorized FPI values.

In one embodiment addressing QoS interworking between the NG and EPC,the WTRU may perform a modify bearer request procedure to establishdedicated bearers in the EPC system. The modify bearer procedure may beperformed for every active PDU session. A dedicated bearer may then beestablished for different authorized FPI values by the MME.

In one embodiment addressing QoS interworking between the NG and EPC,actions taken by the network as described herein may be the result ofactions taken by the WTRU for QoS management.

QoS treatments in either EPC or NG systems may be flow specific wheretraffic flows may need to be detected and recognized before they can beassociated with certain QoS profiles. For IP data flows the traffic flowdetection may be relatively straight forward as IP tuples can beconveniently used to form Traffic Flow Templates (TFT) or packetfilters. Non-IP data flows, however, may be handled differently than IPdata flows. Non-IP data may be carried in a separate PDU session fromIP-based PDU sessions, and/or there may be no mixed IP data flows and/ornon-IP data flows in one single PDU session. Further, within one non-IPPDU session there may be multiple non-IP data flows. In one or moreembodiments, procedures and rules may be developed to performdifferentiated QoS treatment as may be required for multiple non-IP dataflows inside one PDU session. These rules and procedures may relate tonon-IP traffic detection and identification. Additionally, in areflective rule situation a WTRU may need to recognize UL data receivedfrom its non-IP application as a counter part of received DL data so theWTRU can apply the same QoS marking as received from the DL data.

In one embodiment for addressing QoS handling for non-IP data flows,each non-IP data flow may have a data header of a certain format. Forexample, there may be several types of non-IP data header formats: 1)One type of header format may be standardized, and in the header thereis at least a pair of information elements that may be reversed for theUL and DL (e.g., Ethernet (802.3) or WLAN MAC (802.11) packets have apair of “source address” and “destination address” in the header); 2)Another type of header format may be standardized, but may not have apair of information elements that are reversed for the UL and DL; and 3)Another type of header format may not be standardized, or may only bestandardized in a certain industry/application.

For the third example type of non-IP data format, these header formatsmay be less well-known and may be proprietary. For the first and secondexample types of non-IP data formats, these header formats may bestandardized and/or known, but they may still be hard to detect if thereare other non-IP data flows of different data formats mixed within thesame PDU session since there is no distinctive “signature” informationelement in the header that can unambiguously point to a specific dataformat.

FIG. 7 shows an example procedure for QoS rule generation or applicationfor non-IP data that uses known data protocols. In one embodiment, theWTRU 704 may receive 720 explicit information of the data protocol usedin a communication request from a non-IP data application 702. Suchinformation may contain the name of the data protocol, such as “802.3”or “Ethernet”, the version number, and other related information. TheWTRU 704 may include the data protocol information in the PDU sessionestablishment request message sent 721 to the SMF 706 in the NGC. If theNGC supports the requested data protocol it may confirm the PDU sessionestablishment, otherwise it may reject the request.

The SMF 706 that handles the non-IP PDU session may be configured with adefault QoS rule and it may apply the default QoS rule for some or allof the non-IP data flows in the non-IP PDU session that uses the samedata protocol. For those non-IP data flows that the default QoS ruleapplies to, the traffic template or packet filter for traffic detectionmay not be necessary. The SMF 706 may also request 722 the default QoSrule for the non-IP PDU session from the policy function 710 in the NGC,which may respond 723 with the default rule back to the SMF 706. The SMF706 may provide 724 the same default QoS rule to the WTRU 704 during thePDU session establishment procedure.

For some non-IP data flows 725 coming from a non-IP server 712, the SMF706 may also be able to receive 727 QoS rules which include the trafficdetection information generated 726 by the policy function, similar tolegacy EPC QoS policy framework. Once the SMF 706 receives the QoSrules, it may send them for installation in the UP-GW 708. The trafficdetection information may be specific to the non-IP data protocol usedby the PDU session. For example, the source MAC address and destinationMAC address may be used as part of a TFT if the Ethernet data format isused. If the UL TFT can also be derived, which may be the case whenthere is a pair of reversible information elements available, such assource and destination address, the SMF 706 may construct the UL non-IPTFTs for some non-IP data flows and provide 729 them to the WTRU in asession management procedure, such as a QoS rule update.

If the WTRU receives an application data request from another non-IPapplication that requires a different data protocol, it may initializethe establishment of a separate PDU session for the different dataprotocol.

When a WTRU receives non-IP data from an application, the data may beaccompanied with a Data Protocol indication and the WTRU may use thisinformation to map the data to the corresponding non-IP PDU session thatwas previously created. If the UL QoS rule is available for the dataflow, the WTRU may use the traffic detection rule to detect the data andapply the associated QoS profile (e.g., inserting QoS markings in the ULdata), otherwise the WTRU may use the default QoS rule if available.

The RQoS treatment is also possible if there is a pair of reversibleinformation elements in the header.

FIG. 8 shows an example procedure for QoS rule generation for non-IPdata that uses proprietary data protocols. In one embodiment, if thedata protocol used by the non-IP application is not standardized orknown, some distinctive “signature information” may be carried in thedata header and the NGC may utilize that signature information togenerate a non-IP traffic detection rule and thus be able to provide aQoS rule for this non-IP data flow. One example of signature informationcarried in the non-IP data header may be a special coded flag octet oroctets, such as “0x0FAF” in the first two octets of the header, whichmay identify a certain non-IP application. Another example of signatureinformation carried in the non-IP data header may be a coded Service IDor Application ID in the header.

In FIG. 8, the WTRU 802 may send a PDU Establishment Request 820 to anSMF 804 where the PDU type is non-IP. The SMF 804 may send a PDUEstablishment Response 821 to the WTRU 802 using a default QoS rule thatthe SMF 804 may have been pre-configured with 822. These default rulesmay be a set of traffic detection rules for non-IP applications, andeach rule may include one or more of the following information: 1) thesignature info that is supposed to be carried in the data header (suchas “0x0FAF”); 2) the location of the signature info in the header (suchas the first and second octet of the header); and 3) the length of theheader. The SMF 804 may also install 823 these traffic detection rulesin the corresponding UP-GW or UP traffic detection function 806 when thePDU session for the non-IP application is established. The default QoSprofile associated with each traffic detection rule may also beconfigured in the SMF 804 and installed in the UP functions. The QoSprofile may be a set of QoS parameters such as 5QI, allocation andretention policy (ARP), or the like. A QoS rule may be used to identifywhich QoS flow that a traffic flow belongs to and may have packetfilters to map traffic flows resulting in a QoS flow ID. A QoS flow IDmay be associated with a standard or non-standard QoS profile.

The UP-GW or the traffic detection function 806 may generate a trafficdetected event 825 to the SMF 804 upon the detection of the certainnon-IP data flow 824 from a non-IP server 810 according to the installeddetection rules. If the default QoS profile is not available at theUP-GW or the traffic detection function 806 for the detected non-IP dataflow, the SMF 804 may, upon detecting the non-IP traffic, generate 826 acorresponding QoS profile on its own or retrieve it from the policyfunction, and then provide it for installation 827 to the UP-GW or thetraffic detection function 806.

The SMF 804 may provide 828 the same traffic detection rules andassociated QoS profile to the WTRU so the WTRU can use them for the ULQoS rule.

RQoS treatment is also possible for this type of non-IP data. Becausethe UL data and DL data carry the same signature information, the WTRUmay be able to directly use the DL QoS marking for the UL data thatbears the same signature information as long as the WTRU is providedwith the traffic detection rule about where to find the signature info.

In one embodiment, the use of RQoS may be dependent on an indicationfrom the WTRU, although the network may still decide to not apply RQoS.In circumstances where the WTRU starts in an RQoS enabled network, theWTRU may indicate (i.e., to an SMF) its support for RQoS during a PDUsession establishment. However, the WTRU may not be able to indicatesupport for RQoS if a PDU establishment procedure is not performed, suchas in cases where the WTRU actually starts in the EPC where RQoS is notsupported. For example, a WTRU may be capable of multi-RAT technology,such as E-UTRAN and 5G NR, and may first register with an EPC. The WTRUmay have at least one PDU session in the EPC but cannot indicate supportfor RQoS since RQoS may not be supported in the EPC. At a later time,the WTRU may move and may undergo an inter-system change to a 5G CN,where the WTRU's PDU connection(s) will be moved to the 5G system wereRQoS is supported, However, since the connections were already createdin the EPC and now handed over to an NGC of 5G, the WTRU may not have anopportunity to indicate its support for RQoS in the NGC since the PDUestablishment procedure has already been performed in the EPC. As such,the network may not be able to use RQoS for this WTRU until the WTRUestablishes a new PDU session where an RQoS indication can be sent.Embodiments and procedures described herein may address the abovescenario to enable a WTRU to send indications to enable use of RQoS fora PDU session that is already activated in a prior system related to aninter-system change.

Additionally, the embodiments and procedures as discussed herein mayalso be applicable to other features other than addressing RQoS duringan intersystem change, such as where an ability or action is supportedin one system but not a second system that the WTRU us transitioning toor from. For example, these techniques may also apply for a case wherethe WTRU supports a feature that is only available in LTE or the EPC butthe WTRU is starting in a 5G NGC system first.

In one example, the WTRU may have policies or may be configured withinformation that allows it to determine which PDU sessions (e.g., basedon APN or DDN) the WTRU supports RQoS. The indication of RQoS may bebased on the WTRU being supportive of RQoS or the support may beindicated for specific PDU sessions; the embodiments discussed hereinmay apply to both.

The WTRU may send an indication of its RQoS support when it registerswith an EPC system. The indication may be sent in mobility managementmessages or session management messages, or both. For mobilitymanagement messages, the WTRU may send this indication (or otherindications for other NGC features or capabilities) in all NAS messagesand not only in registration messages.

For the WTRU attaching or registering (either due to existing triggersfor registration messages or due to inter-system change to EPC, such asfrom NGC), the WTRU may include this indication in the registrationmessage, such as an Attach Request or Tracking Area Update request. Notethat the latter may be due to a periodic registration. Moreover, theWTRU may send this indication in session management messages as well,either standalone or piggybacked in mobility management messages, suchas an Attach Request.

The WTRU may indicate its support for RQoS using a specific informationelement (IE) or a bit where a value of one indicates “RQoS Supported”and a value of zero indicates “RQoS Not Supported” or vice versa.Alternatively, a set of bits (e.g. at least one octet) may be used toindicate the support of at least one feature such as RQoS. Each bitposition may correspond to a feature or support of a particularoperation or capability (e.g., RQoS). The WTRU may include any of theseindications in mobility management or session management messages.

Alternatively, all of the indications proposed above (e.g., anindication for RQoS, etc.), may be included in a container that isstored and transparently passed to an NGC (e.g., the Access and MobilityManagement Function (AMF)) during an inter-system change. The containermay include mobility management or session management relatedinformation such as capabilities at the mobility management or sessionmanagement level. Furthermore, the WTRU may send such information inseparate mobility management and session management containers whereeach container has capability or feature support information related tomobility management and session management, respectively,procedures/features in the 5G system (or for an LTE system in case theWTRU is first in a 5G system). This container may be called a “UE CNTransparent Container” (UCTC) and may contain information for bothmobility management and session management, or there may be two separatecontainers for each mobility management and session management. The WTRUmay send this container or information in mobility management or sessionmanagement messages.

Alternatively, the WTRU may include its support and desire to use RQoSin a Protocol Configuration Option (PCO) IE that is sent in sessionmanagement messages (e.g., PDN Connection Request) or in mobilitymanagement messages. This may be an RQoS indication for all of the PDU'sconnections, per PDU connection, or per Access Point Name (APN)/DataNetwork Name (DNN). For example, during a PDN connection establishmentin EPC, the WTRU may include a new indication for RQoS in the PCO or inthe extended PCO (ePCO). A new value for the RQoS indication in the(e)PCO may be defined for both cases. When the WTRU sends the (e)PCO tothe network, and when the network responds back to the WTRU, it may alsoinclude an RQoS indication in the (e)PCO that is included in the NASmessage towards the WTRU.

The MME may receive a NAS message, optionally from a WTRU, with a newindication for the support or RQoS. The MME may save this informationand send it towards the SGW/PGW-C. The MME may use a new indication onthe interface between the MME and the SGW/PGW-C to reflect the supportof RQoS by the WTRU, or it may send the same indication (e.g., in PCO orePCO) towards the SGW/PGW-C. The PGW-C may also be assumed to be the SMFor it may support the functions of an SMF. Further, the MME may firstverify against local policies or subscription information to determineif the use of RQoS for the WTRU in question is permitted, for example ina 5G system. If verification is successful, then the MME may forwardthis indication to the SGW/PGW-C.

The MME may also store the received RQoS information in the WTRU contextand then forward the RQoS capability to the AMF upon inter-system change(e.g., as part of the session management context). The AMF may then sendthis capability to one or more SMFs/PGW-C during the handover from EPSto the 5G system.

The PGW-C may receive a message, for example from the SGW/MME,associated with a WTRU and the message may indicate that the WTRUsupports RQoS. The indication may be a new indication over the S11/S5-Cinterface or it may be included in the PCO or ePCO. The SGW/PGW-C mayverify (e.g., using local policies or subscription information) if theWTRU is allowed to use RQoS, for example in the 5G system. Ifverification is successful, the SGW/PGW-C may save this information inthe WTRU's context. The PGW-C/SGW may send (e.g., in a response messagetowards the SGW/MME) a new indication (e.g., in the form of a new valuein the PCO or ePCO) that the use of RQoS is allowed for the WTRU, forexample in the 5G system. The MME may receive an indication from anothernetwork node, such as the SGW/PGW-C, that the use of RQoS is allowed forthe WTRU. The MME/SGW may save this information in the WTRU's context.The SGW may forward this indication to the MME. The MME may forward thisindication to the WTRU in mobility management or session managementmessages. The MME may use a new indication in the NAS message or it mayinclude this indication in the PCO or ePCO, optionally as received fromthe SGW/PGW-C.

The WTRU may receive in a NAS mobility management or session managementmessage an indication that the use of RQoS is supported/allowed,optionally for a target system such as 5G when the WTRU performsinter-system change to the target system. The WTRU may save thisinformation and use it as a trigger to include support for RQoSindication when it performs an inter-system change to a target system(e.g., 5G system).

FIG. 9 shows an example of a WTRU procedure to enable RQoS for one ormore PDUs after an inter-system change. Upon performing an inter-systemchange to a target system (e.g., 5G system), a WTRU 902 may include anindication for the support or desire to use the RQoS feature. The WTRUmay communicate with a network node 904 of the target system (e.g., 5Gsystem). The network node 904 may be any node, reached directly orindirectly, in an NGC such as a gNB, AMF, SMF, or a UPF. The WTRU 902may include the indication in the NAS mobility management message orsession management message, or both. The WTRU 902 may include theindication as a new IE or as a new value in a PCO or ePCO IE. The WTRUmay send a PDU modification request 910 to inform the 5G system that itwants to use, or it supports the use of, RQoS for one or more PDUssession(s) that has already been established in a previous system (e.g.,the EPC). The WTRU may perform the PDU session modification procedurefor all or a subset of PDU sessions transferred from the EPC to NGC of a5G system. Alternatively, the WTRU 902 may include this message in anyNAS session management message, such as when the NAS session managementmessage is a PDU connectivity request, such as a registration request,with a type set to “handover”. The WTRU 902 may include the indicationfor every PDU session registration request that it wants to handoverform a source system (e.g., from the EPC) to a target system (e.g., to aNGC). In one instance, the indication may already be included if theWTRU 902 has already sent an RQoS indication for the same PDU while theWTRU 902 was in the source system (e.g., EPC), such as when the WTRU 902receives an acknowledgement from the source system (e.g. EPC) that RQoSfor the target system (e.g., NGC) is allowed, as discussed herein. Oncethe indication has been received at the network node 904 of the targetsystem, the network node 904 may respond with an acknowledgement (ACK)912 of the indication. After the WTRU 902 receives the ACK 912 then itmay proceed with sending PDUs with specific RQoS 914. Alternatively, theWTRU 902 may not require an ACK, and the WTRU 902 may begin sending PDUswith specific RQoS after the inter-system change is complete.

Alternatively, the WTRU may be configured to deactivate and reactive itsPDU sessions so that it can include the RQoS support indication when itperforms an inter-system change from a source system (e.g., EPC) to atarget system (e.g., NGC).

Upon an inter-system change to a NGC, the WTRU may include an indicationin the NAS mobility management and/or session management messages thatit desires or supports the use of RQoS, and it may do this for all PDUsessions that need to be transferred to the NGC, or regardless of allPDU sessions that need to be transferred. The NGC, such as the AMF, SMF,or both, may verify against local policies or subscription informationif the WTRU is allowed to do so. The SMF or AMF or both, may respond tothe WTRU and indicate the use of RQoS is either allowed or not allowed,for example per PDU session.

The AMF may request context information from the MME, for a WTRU thathas performed inter-system change from EPC to NGC. The MME may forwardany indications about the use or support of RQoS that it may havereceived from the WTRU when it was in the EPC.

In one embodiment there may be an indication of network slice selectionassistance information (S-NSSAI) for EPC-NGC inter-working. In a versionof LTE there may be no network slicing concept; consequently, when a PDNconnection is established in the EPC it may not be associated with aparticular slice. However, the same PDN connection may be transferred tothe NGC during an inter-system change from EPC to NGC. Since the PDUsession in the NGC may be associated to a particular network slice, whenthe PDN connection from LTE is handed over to the NGC, the WTRU may needto have knowledge about the slice associated with the NGC PDU session.There may be procedures that are used to inform the WTRU about the slicecorresponding to a PDU session that was originally established in theEPC system.

In one example demonstrating S-NSSAI indication when interworking withEPC and NGC, the WTRU may include one or more S-NSSAI information in theProtocol Configuration Option (PCO) part of the PDN connection requestNAS message in an EPC, such as based on the configured (Network sliceselection policy) NSSP at the WTRU. As described earlier, the PCO partof the message may be transparent to the MME hence S-NSSAI informationmay be stored in the PGW-C/SMF node at the EPC during the PDN connectionestablishment procedure. The WTRU may receive the selected S-NSSAI inthe PCO of the PDN connection accept message from the EPC. Note that itmay be possible for the EPC network to send the S-NSSAI in the PDNconnection accept message even if this information is not included bythe WTRU in the PDN connection request message. In any case, thePGW-C/SMF may check the local policy, WTRU subscription and/or interactwith other network nodes (e.g., NSSF, HSS/UDM) to select the S-NSSAI forthe PDN connection. The selected S-NSSAI may then be returned to theWTRU in the PDN connection accept message.

In another example, the SMF/PGW-C may not send S-NSSAI information tothe WTRU during the PDN connection procedure in LTE. The SMF/PGW-C maystore the S-NSSAI information (if received by the WTRU in the PCO). TheSMF/PGW-C may then send the stored S-NSSAI values to the AMF during theintersystem change (e.g., EPC to NGC handover or EPC to NGC idle modemobility). If multiple PDN connections are transferred to the NGC, thenSMF(s) corresponding to each PDU session may send the S-NSSAIinformation to the AMF during the intersystem change. The AMF, based onthe allowed NSSAI and/or the local policy, may determine S-NSSAIassociated with the PDU session. The AMF may then return the determinedS-NSSAI back to each SMF. The SMF may then store this information in thePDU session context or the WTRU SM context. Alternatively, when the AMFreceives the SMF/PGW-C address during the inter-system change, the AMFmay determine the S-NSSAI for each active PDU session based on the SMFinformation and/or allowed NSSAI. The AMF may then send the S-NSSAI toSMF corresponding to each PDU session.

When the SMF receives the S-NSSAI associated with a PDU sessiontransferred from the EPC, each SMF may trigger a network initiated PDUsession modification procedure. The PDU modification message to the WTRUmay include the S-NSSAI for the corresponding PDU session.

It may also be possible that when the WTRU receives the allowed NSSAIafter registration update procedure in the NGC upon intersystem change,the WTRU determines that the PDU sessions in the NGC are not associatedwith an S-NSSAI. The WTRU may therefore send the S-NSSAI to the network(e.g., AMF and SMF) by triggering the PDU session modification procedurefor each PDU session transferred from an EPC to an NGC.

Although features and elements are described above in particularcombinations, one of ordinary skill in the art will appreciate that eachfeature or element can be used alone or in any combination with theother features and elements. In addition, the methods described hereinmay be implemented in a computer program, software, or firmwareincorporated in a computer-readable medium for execution by a computeror processor. Examples of computer-readable media include electronicsignals (transmitted over wired or wireless connections) andcomputer-readable storage media. Examples of computer-readable storagemedia include, but are not limited to, a read only memory (ROM), arandom access memory (RAM), a register, cache memory, semiconductormemory devices, magnetic media such as internal hard disks and removabledisks, magneto-optical media, and optical media such as CD-ROM disks,and digital versatile disks (DVDs). A processor in association withsoftware may be used to implement a radio frequency transceiver for usein a WTRU, UE, terminal, base station, RNC, or any host computer.

What is claimed:
 1. A method implemented by a wireless transmit/receiveunit (WTRU) for handling quality of service (QoS) during an inter-systemchange, the method comprising: sending a protocol data unit (PDU)modification request to a session management function (SMF) network nodeindicating support for reflective quality of service (RQoS) upon aninter-system change of the WTRU from an Evolved Packet System (EPS) to a5G System (5GS) network; receiving an indication that the modificationrequest was received; receiving first data in a PDU session with aspecific QoS; and sending second data in the PDU session using thespecific QoS in response to receiving the first data and the indicationthat the modification request was received.
 2. The method of claim 1,wherein the RQoS is specific to a plurality of PDU sessions.
 3. Themethod of claim 1, wherein the request includes Session Management (SM)or Mobility Management (MM) information.
 4. The method of claim 1,wherein the request is included in an attach procedure or a trackingarea update (TAU).
 5. The method of claim 1, further comprisingreceiving a traffic flow template (TFT) including a QoS mapping, whereinthe TFT indicates the specific QoS for sending the data.
 6. A wirelesstransmit/receive unit (WTRU), comprising: a processor; a transmitteroperatively coupled to the processor, the transmitter configured to senda protocol data unit (PDU) modification request to a session managementfunction (SMF) network node indicating support for reflective quality ofservice (RQoS) upon an inter-system change of the WTRU from an EvolvedPacket System (EPS) to a 5G System (5GS) network; a receiver operativelycoupled to the processor, the receiver configured to receive anindication that the modification request was received; the receivingconfigured to receive first data in a PDU session with a specific QoS;and the transmitter configured to send second data in the PDU sessionusing the specific QoS in response to receiving the first data and theindication that the modification request was received.
 7. The WTRU ofclaim 6, wherein the RQoS is specific to a plurality of PDU sessions. 8.The WTRU of claim 6, wherein the request includes Session Management(SM) or Mobility Management (MM) information.
 9. The WTRU of claim 6,wherein the request is included in an attach procedure or a trackingarea update (TAU).
 10. The WTRU of claim 6, wherein the receiver andprocessor are further configured to receive a traffic flow template(TFT) including a QoS mapping, wherein the TFT indicates the specificQoS for sending the data.